I have added test groups for node14 and node16 and we have a similar problem we had before. AWS SDK clients are bundled by esbuild, the layer has all utilities, but the imports of AWS SDK can not be found.

I am digging into esbuild and CDK bundling, and will also check SAM examples.

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

For the record and future readers, at this point the Lambda Layer includes all Powertools utilities and the AWS SDK clients for the services used by them (SSM, Secrets Manager, DynamoDB, and AppConfig).

The total size is 10MB unzipped, we were able to shave off 8MB (-45%) by removing types, and ESM distributions of the SDKs that are shipped, and other files not needed at runtime that are shipped with some of the dependencies.

There's a potential for additional optimization that would allow to decrease the Layer size by 35-50% (based on initial tests), however we have decided to not pursue it at this time mainly because of other competing priorities.

The optimization would involve creating a barrel file (i.e. sdk/index.js) that imports and re-exports only the clients and methods of the SDK used in Powertools, i.e. :

import {
  AttributeValue,
  DeleteItemCommand,
  DynamoDBClient,
  DynamoDBClientConfig,
  DynamoDBServiceException,
  GetItemCommand,
  PutItemCommand,
  UpdateItemCommand,
} from '@aws-sdk/client-dynamodb';
import { marshall, unmarshall } from '@aws-sdk/util-dynamodb';

export {
  AttributeValue,
  DeleteItemCommand,
  DynamoDBClient,
  DynamoDBClientConfig,
  DynamoDBServiceException,
  GetItemCommand,
  marshall,
  PutItemCommand,
  unmarshall,
  UpdateItemCommand,
};

the file would then be run through esbuild like:

npx esbuild sdk/index.js --bundle --outfile=tmp/nodejs/node_modules/@aws-lambda-powertools/commons/lib/sdk/index.js --platform=node --target=node14

this would generate an optimized (& potentially minified) version of the SDK that bundles only the code needed. We would then have to programmatically change the imports within the Powertools code to require this file rather than the SDK, i.e.

const client_dynamodb_1 = require("@aws-sdk/client-dynamodb");
const util_dynamodb_1 = require("@aws-sdk/util-dynamodb");

would become

const client_dynamodb_1 = require("../../../commons/lib/sdk");
const util_dynamodb_1 = require("../../../commons/lib/sdk");

We were able to test this and confirm that: 1/ a Layer created with this method works with all Node.js runtimes, 2/ the total size is significantly lower than the current one.